Compiling optimized entry points for local-use-only function pointers

ABSTRACT

Embodiments relate to using a local entry point with an indirect call function. A compiler is provided to determine and indicate in the program code that the function pointer value resulting from a non-call reference of a function symbol is solely used to perform indirect calls in the same module, e.g. local-use-only. The compiler loads an address of a function through use of a symbolic reference. When the compiler determines that the value employed by the symbolic reference is used exclusively to perform an indirect function call, the compiler proceeds to resolve a local entry point address of the function, thereby reducing a quantity of operations to be executed.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application is a continuation patent application claiming thebenefit of the filing date of U.S. patent application Ser. No.15/332,666 filed on Oct. 24, 2016 and titled “Compiling Optimized EntryPoints for Local-Use-Only Function Pointers”, now pending, the entirecontents of which are hereby incorporated by reference.

BACKGROUND

The present embodiments relate to generally to computer systems andglobal and local entry points for a callee function and optimization ofa caller function. More specifically, the embodiments relate to allowinguse of the local entry point with an indirect function call.

In computer software, an application binary interface (ABI) describesthe low-level interface between an application module and the operatingsystem or between the application module and another application module.The ABI covers details such as data type, size, and alignment; thecalling conventions which control how function arguments are passed andhow return values are retrieved; the system call numbers and how anapplication should make system calls to the operating system; and in thecase of a complete operating system ABI, the binary format of objectfiles, program libraries, and so on. Several ABIs (e.g., the InteractiveUnix ABI allows a wide range of programs to run on a variety of Unix andLinux variants for the Intel x86 architecture) allow an applicationprogram from one operating system (OS) supporting that ABI to runwithout modifications on any other such system, provided that necessaryshared libraries are present, and similar prerequisites are fulfilled.

The program development cycle of a typical application program includeswriting source code, compiling the source code into object files,building shared libraries, and linking of the object files into a mainexecutable program. Additional preparation, including loading of themain executable program and loading of the shared libraries forapplication startup occurs before the application is executed on aparticular hardware platform.

The compiler works on a single source file (compile unit) at a time togenerate object files. The compiler generates object code withoutknowing the final address or displacement of the code/data.Specifically, the compiler generates object code that will access atable of contents (TOC) for variable values without knowing the finalsize of the TOC or offsets/addresses of various data sections.Placeholders for this information are left in the object code andupdated by the linker. A TOC is a variable address reference table thatis utilized, for example in an AIX environment, to access programvariables in a manner that supports shared libraries and is datalocation independent. A similar structure, referred to as a globaloffset table (GOT), performs a similar function (e.g., indirect anddynamically relocatable access to variables) in a LINUX environment. Onedifference between a TOC and a GOT is that a TOC may contain actualdata, where a GOT only contains addresses (pointers) to data. In theLinux PowerPC 64-bit environment the TOC contains the GOT section plussmall data variables.

A static linker combines one or more separately compiled object filesderived from distinct source files into a single module, and builds asingle GOT and/or TOC for the module that is shared by files in themodule. An executing application includes at least one module, astatically linked module typically containing the function main as wellas, optionally, several other functions, sometimes also known as themain module. Some applications may be statically linked, that is, alllibraries have been statically integrated into the main module. Manyapplications also make use of shared libraries, sets of utilityfunctions provided by the system or vendors to be dynamically loaded atapplication runtime and where the program text is often shared betweenmultiple applications.

Each module in a computer program may have a different TOC pointervalue. The TOC register or GOT register (referred to hereinafter as theTOC register) may therefore be saved and restored for each functioncall, either by a procedure linkage table (PLT) stub code segment, or bythe callee function in conventions where the TOC register is treated asa preserved (i.e., callee-saved) register.

SUMMARY

A system, computer program product, and method are provided for allowinguse of the local entry point with an indirect function call.

In one aspect, a system is provided with an indirect function callconfiguration, and a processor operatively coupled to memory. A compileris provided in communication with the processor in order to generateprogram code for an application module. The generation of program codeincludes using a first symbolic reference to load a first address of afunction. An employed value of the first symbolic reference isdetermined to be used exclusively to perform the indirect function callin the application module. Thereafter, the compiler indicates that thefirst symbolic reference can be resolved using a local entry pointaddress of the function in the generated program code.

In another aspect, a computer program product is provided to resolvefunction addresses. The computer program product includes a computerreadable storage device with embodied code that is configured to beexecuted by a processor. More specifically, computer program code isembodied to configure an indirect function call configuration. A firstsymbolic reference is used to load a first address of a function, and anemployed value of the first symbolic reference is determined to be usedexclusively to perform the indirect function call in the firstapplication module. Thereafter, an indication in the program code ismade that the first symbolic reference can be resolved using a localentry point address of the function.

In yet another aspect, a method is provided to resolve functionaddresses. An indirect function call configuration is configured. Afirst symbolic reference is used to load a first address of a function,and an employed value of the first symbolic reference is determined tobe used exclusively to perform the indirect function call in the firstapplication module. Thereafter, an indication in the program code ismade that the first symbolic reference can be resolved using a localentry point address of the function.

These and other features and advantages will become apparent from thefollowing detailed description of the presently preferred embodiment(s),taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The subject matter which is regarded as embodiments is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe embodiments are apparent from the following detailed descriptiontaken in conjunction with the accompanying drawings in which:

FIG. 1 depicts a computer system for a global entry point and a localentry point for a callee function.

FIG. 2 depicts a block diagram for illustrating an embodiment of anindirect call configuration.

FIG. 3 depicts a flow chart illustrating an embodiment of how a compilerwill determine and indicate the function pointer values are forlocal-use-only.

FIG. 4 depicts a flow chart illustrating an embodiment of how a linkerwill interpret the information indicated from a compiler and resolve therelocation.

FIG. 5 depicts a flow chart illustrating an embodiment of whenrelocation cannot be fully resolved by a linker and is resolved by aloader.

FIG. 6 depicts a flow chart illustrating an embodiment of how a compilerwill determine and indicate the function pointer value from a non-callreference of at least two function symbols are for local-use-only.

FIG. 7 depicts a flow chart illustrating an embodiment of how a compilerwill determine and indicate a function pointer can be localized whileenabling function pointer comparisons.

FIG. 8 depicts a flow chart illustrating an embodiment when relocationis resolved by the linker or the loader.

FIG. 9 depicts a flow chart illustrating an embodiment of employing thecompiler to enable a local function call to be tailored for functionpointer calls.

FIG. 10 a flow chart illustrating an embodiment when the call site isoptimized by the linker.

FIG. 11 depicts a flow chart illustrating an embodiment of the compilerperforming an optimal resolution of a function symbol and an indirectcall site.

FIG. 12 depicts a flow chart illustrating an embodiment of the compilerperforming an analysis of the COLA group.

FIG. 13 depicts a schematic of an example system to implement theprocess shown and described in FIGS. 1 and 3-12.

FIG. 14 is a block diagram illustrating an example of a computersystem/server of a cloud based support system, to implement the processdescribed above with respect to FIGS. 1 and 3-12.

FIG. 15 depicts a block diagram illustrating a cloud computerenvironment.

FIG. 16 depicts a block diagram illustrating a set of functionalabstraction model layers provided by the cloud computing environment.

DETAILED DESCRIPTION

It will be readily understood that the components of the presentembodiments, as generally described and illustrated in the Figuresherein, may be arranged and designed in a wide variety of differentconfigurations. Thus, the following detailed description of theembodiments of the apparatus, system, and method of the presentembodiments, as presented in the Figures, is not intended to limit thescope of the embodiments, as claimed, but is merely representative ofselected embodiments.

Reference throughout this specification to “a select embodiment,” “oneembodiment,” or “an embodiment” means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present embodiments. Thus,appearances of the phrases “a select embodiment,” “in one embodiment,”or “in an embodiment” in various places throughout this specificationare not necessarily referring to the same embodiment.

The illustrated embodiments will be best understood by reference to thedrawings, wherein like parts are designated by like numerals throughout.The following description is intended only by way of example, and simplyillustrates certain selected embodiments of devices, systems, andprocesses that are consistent with the embodiments as claimed herein.

Embodiments for a loader configured to select between a plurality ofentry points of a callee function for a calling function are provided,with embodiments being discussed below in detail. Each function inapplication object code may have a plurality of entry points insertedby, for example, a compiler. The entry points may be inserted at certainlocations within the function for different reasons. Entry points may beused to enter a callee function at a certain point within the code ofthe callee function, which may skip parts of the code within thefunction.

A dynamic shared object (DSO) is an object file that is intended to beused simultaneously (or shared by) multiple applications while they areexecuting. A DSO can be used in place of archive libraries and canminimize overall memory usage since code is shared. Two executables thatuse the same DSO and that run simultaneously have only one copy of theshared components loaded into memory.

The ABI may use a different calling function calling sequence whencalling a function in a different DSO, as opposed to a function in thesame DSO. For example, the Power ELFv2 ABI allows a callee routine toprovide both a global and a local entry point. Callers of that routinemay use the local entry point if caller and callee reside in the sameDSO and share the same TOC pointer value. Other callers must use theglobal entry point. Calling the global entry point is less efficientthan calling the local entry point since program code at the globalentry point must recalculate the TOC pointer value to be used in thecallee routine. Accordingly, the compiler, static linker, and dynamicloader arrange to use the local entry point as often as possible.

Most programming languages allow for direct and indirect function calls.A direct function call takes place when the caller function transferscontrol to one fixed callee routine, e.g. the callee routine is beinginvoked directly through a fixed name or address. An indirect functioncall takes place when the caller function transfers control to afunction identified as being invoked indirectly through a variable, e.g.function pointer variable. In one embodiment, the function pointervariable can be set to refer to any of a set of target functions. At anyplace where a function pointer is set to refer to a particular function,that particular function is identified by a symbol name and the computergenerates code to load that symbol address and store the symbol addressin the function pointer variable. The programming code that loads thesymbol address will include relocations referring to the symbol, and therelocations will be resolved by the static linker and/or dynamic loader.

The static linker and/or dynamic loader determine which entry point touse from the potentially multiple entry points associated with thesymbol. More specifically, the linker generates an application module,and resolves a symbolic reference to a function address. The dynamicloader loads an application module into memory. The dynamic loader mayresolve a symbolic reference to a function address at load time.

FIG. 1 illustrates an embodiment of a computer system (100) for localand global entry points for a target function. Computer system (100)comprises a processor (102) in communication with a main memory (104)across a bus (122). Application object code (106), which is generatedfrom program source code (not shown) by a compiler such as compiler(110), comprises a plurality of functions, and is stored in main memory(104) for execution by processor (102). The application object code(106) may be generated by a compiler that is located on a differentcomputer system from computer system (100). A relocation record (120),which is generated by a compiler, such as a compiler (110), is stored inthe application object code (106) for review by the compiler (110),linker (112), or loader (114). Relocation record (120) may containmultiple pieces of information, such as (120 a), (120 b) and (120 c).The linker (112) may read the relocation record (120) and if necessarygenerate another copy of the relocation into an executable or DSO file(e.g. a dynamic relocation). The linker (112) links the applicationobject code (106) before the application object code (106) is executedby the loader (114). A shared library (108) stores functions that areexternal to application object code (106) and that may be called duringexecution of application object code (106) via external function calls(i.e., calls to functions in other modules). Loader (114) comprises aruntime component and executes the application object code (106). Theloader (114) may inspect the relocation record present in the executableor DSO file while loading the file into a memory, such as main memory(104).

Table of Contents (TOC) register (116) is located in processor (102).TOC register stores a current value of a TOC pointer for the currentlyactive function of application object code (106) or shared library(108). Function address register (118) is also located in processor(102), and holds an address of currently executing functions. In someembodiments, the computer system (100) may further comprise anotherobject code module that is distinct from the application object code(106) and the shared library (108), and the other object code module mayalso contain functions that are called by application object code (106)via external function calls.

In one embodiment, a compiler, such as compiler (110), generatesapplication code (106) from program source code. In one embodiment, thecompiler (110) generates shared library (108). The compiler thatgenerates application object code (106) may be located on anothercomputer system that is distinct from computer system (100). In oneembodiment, another compiler on a third distinct computer may generateshared library (108). During compilation, the compiler createsrelocation record (120) and indicates in the program code whether afunction pointer value is for local-use-only. The function calls in theapplication code (103) are resolved by the compiler (110), linker (112),or loader (114), or a combination thereof. Resolution of the functioncall may occur at different times for different function calls in thesame application code (106). At the time of resolution of a functioncall, the compiler (110), linker (112), loader (114), or combinationthereof, determines (a) whether a function pointer value is forlocal-use-only by examining the program code and (b) whether thefunction is defined in the same module as the reference. The compiler(110), linker (112), loader (114), or combination thereof, then insertsa local point of entry if the answer is positive to both (a) and (b)otherwise, a global point of entry is inserted.

FIG. 2 is a block diagram (200) illustrating an embodiment of anindirect call configuration. There are three application modules,module_(A) (210), module_(B) (220) and module_(C) (230). A targetfunction (212) of an indirect call is defined in module_(A) (210).Module_(B) (220) contains a reference of a symbol (222) to initialize afunction pointer. Module_(C) (230) contains an indirect call (232) thatoccurs through the function pointer. In one embodiment, module_(A)(210), module_(B) (220) and module_(C) (230) are dynamically sharedobjects (DSOs). The determination of the indirect call configuration isdiscussed in further detail with respect to FIGS. 3-6.

Referring to FIG. 3, a flow chart (300) is provided illustrating anembodiment of how a compiler will determine and indicate a functionpointer value is for local-use-only. The compiler determines a functionpointer value resulting from a non-call reference, see (222), of afunction symbol (302). The compiler (110) determines whether thefunction pointer value resulting from a non-call reference (222) of afunction symbol is solely used to perform indirect function calls withinthe same module, e.g. “local-use-only” (304). In order to correctly makethe determination, the compiler (110) may perform an exhaustivecode-flow and data-flow analysis determining all uses of the functionpointer value resulting from a non-call reference (222) to a functionsymbol. This analysis may involve determining (a) that the value isnever returned from the function where it is used, (b) it is stored onlyin function pointer variables that are local to a function, or (c) it isonly stored in function pointer variables that are local to a sourcefile and whose address is never taken. In one embodiment, the compiler(110) tracks all places where a function pointer value is written orinitially read. In one embodiment, the determination is performed byusing an escape analysis, which determines a set of uses for thefunction pointer value. Each use returned by the escape analysis must befurther analyzed to determine if every use is an indirect function callwithin the same module (304) as the non-call reference (222). In oneembodiment, a compiler, such as compiler (110), makes the determinationat step (304) by determining a local live range, L, that is visible inthe local module only. The compiler (110) will determine the transitiveclosure of the live range, L, is only used in a function call within thelocal module. The compiler (110) determines if a reference to a functionsymbol is used to initialize the live range, L.

The response to the determination at step (304) will be indicated in theprogram code. In order for the compiler (110) to indicate theinformation for use by the linker (112) or loader (114), the compiler(110) generates program code that uses relocations associated with thetarget function symbol. The compiler (110) may already generate code toreference a function symbol for non-call purposes thus, the program codemay contain a relocation record (120). In one embodiment, the relocationrecord is an instruction to the linker to fill in a “placeholder” leftin the object code with the actual address of the identified targetfunction. The relocation record (120) contains several pieces ofinformation, including, but not limited to, the location of the“placeholder” (120 a) to be filled in (e.g. by the local entry pointaddress or global entry point address of the target function), the nameof the target symbol (120 b), and a relocation type (120 c) describingwhich of possible multiple actions to perform. The quantity and type ofinformation contained in the relocation record is for illustrationpurposes only and should not be considered limiting.

In one embodiment, in order to pass the information of the determinationat step (304) to the linker (112), the compiler (110) indicates whetheror not the function pointer value is local-use-only in the relocationtype (120 c). For example, if the answer to the determination step (304)is negative, e.g. it is determined there are uses beyond indirect callsin the local module, the compiler will indicate not local-use-only by afirst relocation type (306). In one embodiment, other uses beyondindirect calls in the current module can include function pointercomparisons, conversions to integers or other non-function-pointer types(either via casts or type-punning via unions), or accessing parts of thefunction pointer value in memory. In one embodiment, one class of otheruses can be allowed, while still making a correct local-use-onlydetermination (e.g. a comparison of the value against a NULL functionpointer constant). If the compiler (110) makes a positive determinationat step (304), where the function pointer value is indeedlocal-use-only, the compiler (110) will indicate local-use-only by asecond relocation type (308). In one embodiment, the compiler indicatesto a loader whether or not a symbol reference is local-use-only.Accordingly, the compiler (110) can indicate to a linker whether or nota symbol reference (e.g. function pointer value determined via areference to a function symbol) is designated as local-use-only.

Referring to FIG. 4, a flow chart (400) is provided to illustrate anembodiment of the linker, and more specifically demonstrate how thelinker is employed to interpret the information indicated from acompiler, and to also resolve the relocation of the actual targetfunction address. The linker (112) resolves the relocation of the actualtarget function address by replacing the placeholder within theapplication code, as indicated in the relocation record (120 a) with theactual target address. The linker (112) can use a local entry point or aglobal entry point of the target function for the target address. Asshown, the linker (112) determines whether the program code indicatesthe function symbol reference is local-use-only (402). For example, thelinker (112) may inspect the relocation type (120 c) associated withtarget function symbol in the relocation record (120). If at step (402)the linker (112) determines the relocation type (120 c) is a firstrelocation type (e.g. not local-use-only), the linker (112) replaces theplaceholder indicated by the relocation record (120 a) with the globalentry point associated with the target function (404). However, if atstep (402) the linker determines that the relocation record shows theobject as having a second relocation type (e.g. local-use-only) thelinker proceeds to step (406) to further assess whether the targetfunction is defined in the same module as the function symbol reference.A negative response to the determination at step (406) is followed bythe replacement of the placeholder shown and described in step (404).However, a positive response to the determination at step (406) isfollowed by the linker replacing the placeholder indicated by therelocation record (120 a) with the local entry point associated with thetarget function (408). In one embodiment, at step (408) the linkerremoves the symbolic reference prior to replacing the local entry pointaddress. Accordingly, as shown herein, the linker (112) may resolve alocal-use-only indication from a compiler (110) and use a local entrypoint for resolving a location.

Referring to FIG. 5, a flow chart (500) is provided illustrating anembodiment when a relocation may not be able to be fully resolved by thelinker. In one embodiment, the target function (e.g. the function thatwill be the target of the indirect function call) is not yet known tothe linker (112) (e.g. the current module does not contain any functionwith the function name stored in the relocation record). In oneembodiment, another object that is not in the same module as thefunction symbol reference contains a second function of the same namereferenced by the symbol and Executing and Linking Format (ELF) nameresolution rules require that any use of the function name is resolvedto the second function address (e.g. the symbol refers the secondaddress and the linker/loader will use the entry point associated withthe second function). In one embodiment, the linker (112) cannot make afinal determination that the function in the current module is indeedthe target function referenced by the symbol.

In one embodiment, the linker (112) determines whether or not it canmake the final determination of whether or not the target function isdefined in the same module as the function symbol reference (502). Thelinker (112) cannot make the final decision in scenarios where thelinker (112) does not have access to all of the modules needed tooperate the application module where the function symbol may reference afunction by the same name in another module yet to be found. A positiveresponse to the determination at step (502) is followed by the linker(112) proceeding to determine whether the target function is defined inthe same module as the function symbol reference (504). If the responseto the determination at step (504) is positive, the linker proceeds todetermine if the program code indicates if the function symbol referenceis local-use-only (506). In one embodiment, the linker (112) inspectsthe relocation type (120 c) associated with target function symbol inthe relocation record (120) to complete the assessment at step (506).During this inspection if it is determined that the location type (120c) is the first relocation type, e.g. not local-use-only, the linkerwill replace the placeholder indicated by the relocation record (120 a)with the global entry point associated with the target function (508).However, if at step (506) it is determined that the relocation type (120c) is a second relocation type, e.g. local-use-only, the linker (112)replaces the placeholder indicated by the relocation record (120 a) withthe local entry point associated with the target function (510).Accordingly, as shown herein, there is a plurality of circumstances thatenable the linker to replace the placeholder, either with the globalentry point, see step (506), or with the local entry point, see step(510).

Returning to step (502), if it is determined that the linker cannot makea final decision with respect to whether or not the target function isdefined in the same module as the function symbol reference, the linker(112) leaves a dynamic relocation in the executable file (512), whichcan be resolved at a load time by the loader (114). Similarly, returningto step (504) if it is determined that the target function is notdefined in the same module as the function symbol reference, the linker(112) leaves a dynamic relocation in the executable file at step (512).As shown, following step (512), the loader (114) inspects the dynamicrelocation in the executable file (514). Based on the inspection, theloader (114) determines whether the target function is defined in thesame module as the function symbol reference (516). A negative responseto the determination at step (516) is followed by use of the globalentry point associated with the target function (518). If the responseto the determination at step (516) is positive, the loader proceeds tostep (520). Accordingly, the linker can leave a dynamic relocation whichthe loader can inspect to determine which entry point to use.

At step (520), the loader (114) determines if the program code indicatesif the function symbol reference is local-use-only. A positive responseto the determination at step (520) is followed by use of the local entrypoint associated with the target function (522). A negative response tothe determination at step (520) is followed by use of the global entrypoint associated with the target function as shown in step (518). In oneembodiment, the loader inspects the dynamic relocation and determineswhether the target function is local-use-only. In one embodiment, if theloader determines the target function is not local-use-only, e.g. firstrelocation type, the loader adds a global entry point withoutdetermining the location of the definition of the target function. Asdemonstrated, the final determination of whether to use the global entrypoint or local entry point is under the direction of the loader (114).Accordingly, the process shown herein checks for the local-use-onlyrelocation, and if it is not present, the local entry point is not used.

Referring to FIG. 6, a flow chart (600) is provided illustrating anembodiment of how the compiler (110) determines and indicates thefunction pointer value from at least two non-call references to afunction symbol are for local-use-only. The compiler (110) determinesthe function pointer value(s) resulting from at least two non-callreferences of a function symbol (602). Based on the function pointervalue(s), the compiler (110) determines whether the function pointervalue(s) resulting from at least two non-call references to a functionsymbol is solely used to perform indirect function calls within the samemodule (604). See FIG. 3, step (304) for further details in thedetermination at step (604). A negative response to the determination atstep (604) is followed by the compiler indicating that the functionpointer value(s) are not exclusive for local-use-only by a firstrelocation type (606). However, a positive response to the determinationat step (604) is followed by the compiler (110) merging the at least twonon-call references into a single reference (608) and indicatinglocal-use-only by a second relocation type for the new single reference(610). In one embodiment, the merged referenced is used to initializeboth non-call references. In one embodiment, the compiler (110)indicates a new merged symbol reference is local-use-only to the linker,and in another embodiment, the compiler indicates the local-use-only tothe loader.

Referring to FIG. 7, a flow chart (700) is provided illustrating anembodiment of how a compiler will determine and indicate a functionpointer can be localized while enabling function pointer comparisons.The compiler determines a candidate set of function pointers resultingfrom at least one non-call reference (e.g. (222)) of at least onefunction symbol (702). In one embodiment, the set determined at step(702) includes at least one function pointer. The compiler (110)determines whether the candidate set of function pointers is used solelyto perform indirect function calls within the same module (704) as thefunction symbol reference. In one embodiment, the determination at step(704) includes allowing other uses such as a comparison against a NULLvalue or a comparison against another function pointer. If a negativeanswer to the determination at step (704) is found the function pointeris removed from the candidate set and indicated as not local-use only(706). Accordingly, the initial assessment of the function pointerevaluates a candidate set of functions pointers with respect toperforming an indirect function call, and specifically, the associatedpointer values for indirect function calls within the same module.

If at step (704) it is determined that the function pointer is solelyused to perform an indirect function call within the same module, or incomparisons against a NULL value or a comparison against anotherfunction pointer, as evidenced by a positive response to thedetermination at step (704), the candidate set of function pointers isthen analyzed to determine whether the function pointers may be assignedfrom an external variable (708). The nature of the response to thedetermination at step (708) is followed by an assignment of thecandidate function pointer to one of two groups. As shown, a positiveresponse to the determination at step (708) is followed by the candidatefunction pointer being assigned to a Candidate Assigned from ExternalVariable (CAEV) group (710) indicating a first relocation type (e.g. notlocal-use-only) (722). A negative response to the determination at step(708) is followed by the candidate function pointer being assigned tothe Candidates with Only Local Assignments (COLA) group (712).

Following the COLA group assignment at step (712), the members of theCOLA group are analyzed to determine if a member of the COLA groupcontains a comparison to another function pointer, function pointervalue, or function pointer constant not contained in the COLA group(714). In addition, during step (714) the members of the COLA group areanalyzed to determine if a member variable in the COLA group is assignedfrom a value outside the COLA group. Any member found to have acomparison external to the COLA group and any member having a variablefound to have an assignment external to the COLA group is removed fromthe COLA group. In one embodiment, due to the dynamic nature of the COLAgroup (e.g. varying membership), the process of step (714) is performediteratively until no members are removed from the COLA group during aniteration of the analysis (716). Accordingly, a COLA group is formedhaving members with only comparisons to other members in the COLA groupand members having variables assigned from members within the COLAgroup.

In order to ensure local assignment of the function pointers symbols,function pointer constants assigned to a function pointer variable inthe COLA group or compared with a function pointer variable in the COLAgroup are copied (718). Copying is performed as the original functionpointer constant may be used by an external module. Copying the functionpointer constants enables any external module to use the originalfunction pointer constant and the function pointers in the COLA group touse the copied function pointer constant. In this way, the copiedfunction pointer constant cannot be initialized from an outside module.The remaining COLA group found at step (716) will be indicated in theprogram code as local-entry-pointer-if-local-function (720).

In one embodiment, in order to pass the COLA group found at step (716)to the linker (112), the compiler (110) may indicate a third relocationtype (120 c), e.g. local-entry-pointer-if-local-function. In oneembodiment, if the function pointer contained in the candidate set isonly used to perform indirect function calls within the same module or acomparison against a NULL value at step (704) the compiler (110) maythen indicate the function pointer according to step (308). In oneembodiment, the third relocation type, as described above, is the sameas the second relocation type as described and shown in FIG. 3, e.g.local-use-only. In one embodiment, the functions removed from the COLAgroup are assigned the first relocation type as described and shown inFIG. 3, e.g. not local-use-only. In one embodiment, the compilerindicates to a loader whether or not a function pointer value can beinitialized with a local-entry-pointer-if-local-function in therelocation type. Accordingly, the compiler (110) indicates to a linkerwhether or not a function symbol reference (e.g. function pointer valuedetermined via a reference to a function symbol is designated aslocal-entry-pointer-if-local-function.

In one embodiment, the relocation type designation must to be applied toall function pointers contained in the COLA group, i.e. globally. In oneembodiment, any comparison with a function pointer in the COLA groupshould be resolved within the scope of the same module and localityrules. In one embodiment, where each function pointer constant used inconjunction with function pointer variables assigned to the COLA groupare copied and the function pointer constants have the same relocationtypes, all instances of the function pointer constants are resolved inthe same manner by the linker or loader.

Referring to FIG. 8, a flow chart (800) is provided illustrating aprocess for resolving relocation by the linker or the loader. As shownherein, the linker (112) determines whether or not it can make the finaldetermination of whether or not the target function is defined in thesame module as the function symbol reference (802). The linker (112)cannot make the final decision in scenarios where the linker (112) doesnot have access to all of the modules needed to operate the applicationmodule, such as where the function symbol may reference a function bythe same name in another module yet to be found. A negative response tothe determination at step (802) is followed by the linker (112) leavinga dynamic relocation in the executable file (812), which can be resolvedat a load time by the loader (114). A positive response to thedetermination at step (802) is followed by the linker (112) proceedingto determine whether the target function is defined in the same moduleas the function symbol reference (804). If the response to thedetermination at step (804) is positive, the linker (112) proceeds todetermine if the program code indicates if the function symbol referenceis local-entry-pointer-if-local-function (806). A negative response tothe determination at step (804) is followed by the linker (112) leavinga dynamic relocation in the executable file, as shown in step (812).Accordingly, the linker (112) does not add an entry point when it doesnot have access to the information to make the determination of whetheror not the target function is defined in the same module as thereference.

As shown, during step (806), the linker (112) inspects the relocationtype (120 c) associated with a target function symbol in the relocationrecord (120). During this inspection if it is determined that thelocation type (120 c) is the first relocation type, e.g. notlocal-use-only, the linker (112) replaces the placeholder with theglobal entry point associated with the target function (808). However,if at step (806) it is determined that the relocation type (120 c) is athird relocation type, e.g. local-entry-pointer-if-local-function, thelinker (112) replaces the placeholder indicated by the relocation record(120 a) with the local entry point associated with the target function(810). Accordingly, a linker assigns a local entry point if the linkerdetermines the target function is defined in the same module as thereference.

As shown, following a negative determination at step (802) or step(804), and more specifically, following step (812), the loader (114)inspects the dynamic relocation left by the linker (112) in theexecutable file (814). Based on the inspection, the loader (114)determines whether the target function is defined in the same module asthe function symbol reference (816). A negative response to thedetermination at step (816) is followed by use of the global entry pointassociated with the target function (818). However, a positive responseto the determination at step (816) is followed by use of the local entrypoint associated with the target function (820). In one embodiment, theloader inspects the dynamic resolution and determines whether the targetfunction is local-entry-pointer-if-local-function. In one embodiment, ifthe loader determines the target function is not local-use-only, e.g.first relocation type, the loader adds a global entry point withoutdetermining the location of the definition of the target function.Accordingly, as demonstrated, the determination of whether to use theglobal entry point or local entry point is demonstrated in FIG. 8 to beunder the direction of the linker (112) or loader (114).

Referring to FIG. 9, a flow chart (900) is provided illustrating anembodiment of a method of employing the compiler to enable an indirectfunction call to be tailored for local calls. The compiler determines acandidate set of at least one function pointer resulting from at leastone non-call reference (e.g. (222)) of at least one function symbol(902). From the candidate set of function pointers, the compiler (110)determines whether the candidate set of at least one function pointeris/are used to perform indirect function calls within the same module(904) as the function pointer. A negative response to the determinationstep (904) is followed by removal of the function pointer from thecandidate set and the compiler (110) does not annotate the associatedindirect function call site (906). However, a positive answer todetermination step (904) is followed by analysis of the remainingcandidate set to determine whether the function pointers may be assignedfrom an external variable (908). In one embodiment, the function pointeris used both to perform an indirect function call in the same module anda use in another module; examples of other uses are described above.Accordingly, the first part of the method shown herein conducts anassessment of the candidate set of function pointers, including anassessment against a NULL value.

A positive response to the determination step (908) is followed by thecandidate function pointer being assigned to a Candidate Assigned fromExternal Variable (CAEV) group and the compiler (110) does not annotatethe associated indirect call site (910). However, if the response to thedetermination at step (908) is negative, the candidate function pointeris assigned to a Candidates with Only Local Assignments (COLA) group(912). Accordingly, the evaluation of a candidate function pointer atstep (908) includes an assignment of the candidate function pointer toeither the COLA or CAEV group.

Following population of the COLA group at step (912), the members of theCOLA group are analyzed to determine if a member variable in the COLAgroup is assigned from a value outside the COLA group (914). Any membervariable found to have an assignment external to the COLA group isremoved from the COLA group. In one embodiment, the process of step(914) is performed iteratively until no members from the COLA group areremoved during an iteration of the analysis (916). For each memberremaining in the COLA group after step (914) the transitive closure ofthe reaching definition is computed (918). The reaching definitiondetermines variables which can be assigned to the member without anintervening assignment between the variable and the member. The compiler(110) creates a list of one or more elements which may include but isnot limited to a function pointer constant(s) based on the transitiveclosure of the reaching definition. The element(s) are potential targetfunctions of the indirect function call. In one embodiment, the list ofelements includes at least all potential target functions for theindirect function call. In one embodiment, following step (918), thecompiler (110) identifies indirect calls performed with the functionpointer (920). However, if a function pointer is not used to perform anyfunction calls no further actions are taken on that function pointer.Following step (920) if the computed transitive closure at step (918)consists of a single element, the compiler (110) rewrites the indirectfunction call into a direct function call based on the single elementobtained from the transitive closure (924). If the list created by thetransitive closure of step (918) consists of at least two elements, thecompiler (110) provides the list in the program code to a linker inconjunction with the indirect call site (922). Accordingly, the compilerprovides a list of elements associated with the transitive closure of afunction pointer to a linker.

In order to pass the elements in the list of elements created at step(918) to the linker (112), the compiler (110) annotates the indirectcall site. In one embodiment, the compiler (110) will indicate theelements in the list at the indirect call site including a reference toa function symbol identifying a potential target function found bycomputing the transitive closure of the reaching definition. In oneembodiment, the compiler will annotate the indirect call site byreferencing a location containing the list of elements. In oneembodiment, the compiler annotates the indirect call site by referencingmultiple locations. Accordingly, the compiler (110) can indicate to alinker whether or not a call site is annotated by a list of elementsfrom computing the transitive closure of the function pointer.

The list of elements indicated by the compiler, as shown and describedin FIG. 9, may be used by the linker to optimize the indirect call site.Referring to FIG. 10, a flow chart (1000) is provided illustrating anembodiment when an indirect call site is optimized by the linker. Asshown, the linker (112) determines whether there are elements in a listassociated with the indirect call site (1002). If at step (1002) thelinker (112) determines the response to be negative, the linker (112)does not perform any optimization on the call site (1004). However, ifthe response to the determination at step (1002) is positive, the linkerproceeds to resolve the location(s) of the elements in the listassociated with the indirect call site (1006). Accordingly, the linker(112) does not optimize an indirect call site if a list of elements isnot indicated in the program code.

After the linker has resolved the location of the elements in the listat step (1006), the linker (112) determines whether the elements in thelist associated with an indirect call site are defined in the samemodule as the indirect call site (1008). In one embodiment, it isdetermined whether every element in the list associated with an indirectcall site is defined in the same module as the indirect call site. Ifthe response to the determination at step (1008) is positive, the linker(112) optimizes the indirect call site by rewriting it for a local-callonly sequence. In one embodiment, a positive determination at step(1008) is followed by the linker changing the program code at the callsite to omit the loading or restoring of a TOC pointer register. If theresponse to the determination at step (1008) is negative, the processproceeds to step (1004) and does not optimize the indirect call site. Inone embodiment, the compiler performs the operations of the linker.Accordingly, as shown herein the linker optimizes the indirect call siteif the linker determines the list of elements indicated in the programcode associated with a function symbol reference are defined in the samemodule as the function symbol reference.

A callee routine may provide both a global and a local entry point.Callers of that routine may use the local entry point if caller andcallee reside in the same module and share the same TOC pointer value.Callers outside of the module must use the global entry point. It isadvantageous to use local entry points at call sites as well as atsymbolic references to increase the efficiency of the compiler, linkerand loader. Additionally, when the application object code to perform afunction call is executed, the TOC pointer value in the TOC register maybe saved to a TOC save area in the stack frame and later restored fromthe save area. However, if the caller and callee reside in the samemodule and share the same TOC pointer value, the save and restore of theTOC pointer may not be necessary. Optimizing the call site by reducingthe save and the load of a TOC pointer may reduce processor resourceutilization when executing the code. Thus, a method is described belowto efficiently determine a call site(s) which can be optimized forlocal-call only sequences and a function pointer value(s) which can beoptimized for local-use-only.

Referring to FIG. 11, a flow chart (1100) is provided illustrating anembodiment of the compiler performing an optimal resolution of afunction symbol and an indirect call site. As shown, the compiler (110)creates a candidate set of at least one function pointer resulting froma non-call reference of a function symbol (1102). The compiler (110)determines whether the function pointer value(s) resulting from anon-call reference (222) of a function symbol is used to performindirect function calls within the same module as the function symbolreference (1104). If the response to the determination at step (1104) ispositive, the compiler will proceed to step (1108) to further analyzethe candidate set. However, if the response to the determination at step(1104) is negative, the candidate is removed from the set and no furtheroptimization is performed on the function pointer (1106). In oneembodiment, the compiler (110) indicates not local-use-only in theprogram code at step (1106). Accordingly, the compiler (110) candetermine a candidate set of function pointers for further analysis.

As shown, at step (1108) the compiler (110) determines whether thefunction pointer value of a candidate resulting from a non-callreference is solely used to perform indirect function calls within thesame module as the function symbol reference or a comparison againstNULL. If the response to the determination at step (1108) is positive,e.g. it is determined there no uses beyond indirect function callswithin the local module or the other use is a NULL comparison, thecompiler will proceed to indicate in the program code that the functionpointer value is for local-use-only (1110). Following step (1110), thecompiler (110) assigns the candidate function pointer to a Candidateswith Only Local Assignments (COLA) group (1112). However, if theresponse to the determination at step (1108) is negative, the candidateis subject to further analysis at step (1114) before a group assignment.Accordingly, the compiler may indicate a function pointer value islocal-use only and proceed to further optimize the call site of thefunction pointer.

At step (1114), the compiler (110) determines whether the member of thecandidate set may be assigned from an external variable. If the responseto the determination at step (1114) is positive, the candidate functionpointer is assigned to a group referred to as the Candidate Assignedfrom External Variable (CAEV) group (1118) and no optimization isperformed on the group member(s). In one embodiment, the assignment atstep (1118) includes the compiler (110) indicating not local-use-only inthe program code for the member(s). If the response to the determinationat step (1114) is negative, the compiler will proceed to assign thecandidate to the COLA group which is subject to further analysis (1116).Accordingly, the compiler (110) can indicate function symbol referencesthat are not local-use-only.

Members of the COLA group are assigned from steps (1112) and (1116).Referring to FIG. 12, a flow chart (1200) is provided illustratinganalysis of the COLA group. As shown, the compiler (110) determineswhether a member variable is assigned from a value outside of the COLAgroup (1202). Any member variable found to have an assignment externalto the COLA group is removed from the COLA group. In one embodiment, theprocess of step (1202) is performed iteratively until no members fromthe COLA group are removed during an iteration of the analysis (1204).For each member remaining in the COLA group after step (1204), thetransitive closure of the reaching definition is computed, whichcontains a list of elements (1206). In one embodiment, following step(1206), the compiler (110) identifies indirect calls performed with themember function pointer (1208). However, if a member function pointer isnot used to perform any function calls no call site optimization isperformed based on that function pointer (1210). Accordingly, thecompiler determines members of the COLA group that may be optimized attheir call sites.

Following step (1208), if the computed transitive closure at step (1206)consists of a single element, the compiler (110) performs call siteoptimization by rewriting the indirect function call into a directfunction call based on the single element obtained from the transitiveclosure (1212). If the list created by the transitive closure of step(1206) consists of at least two elements, the compiler (110) performscall site optimization by providing the list in the program code to alinker in conjunction with the call site (1214). Accordingly, thecompiler optimizes call sites by providing a list of elements associatedwith the transitive closure of a function pointer to a linker.

Following steps (1210), (1212) and (1214) the remaining members of theCOLA group are subject to further analysis. The members of the COLAgroup are analyzed to determine if a member in the COLA group has anyother use(s) than a function call within the same module as the functionsymbol reference, a comparison to a member of COLA, a comparison to aNULL value, or if the member of the COLA group is externally assigned(1216). Any member found to have other use(s) or is externally assignedis removed from the COLA group. In one embodiment, due to the dynamicnature of the COLA group (e.g. varying membership), the process of step(1216) is performed iteratively until no members from the COLA group areremoved during an iteration of the analysis (1218). Accordingly,additional members may be removed from the COLA group.

The function pointer constants assigned to a function pointer variablein the COLA group or compared with a function pointer variable in theCOLA group are copied in order to ensure local assignment of thefunction pointer constant (1220). Copying is performed as the originalfunction pointer constant may be used by an external module. Copying thefunction pointer constants enables any external module to use theoriginal function pointer constant and the function pointers in the COLAgroup to use the copied function pointer constant. In this way, thecopied function pointer constant cannot be initialized from an outsidemodule. Following step (1220), it is determined whether the COLA memberhas already been designated local-use only (1222). If the response tothe determination at step (1222) is negative, the compiler will proceedto designate in the program code that the non-call reference associatedwith that member is for local-entry-pointer-if-local-function (1224). Ifthe response to the determination at step (1222) is positive, theoptimization is concluded for that group member. Accordingly, members ofthe candidate set may have no optimization, have a function valueoptimized, a function site optimized or combinations thereof.

The process shown in FIGS. 2-12 demonstrate the function of thecompiler, linker, and loader, and more specifically, the processesemployed for resolving aspects of the user of the local entry point withan indirect function call. It is understood that these processes and thefunction of the compiler, linker, and loader are embedded in hardware ofthe underlying computer system. For example, the location holding afunction pointer value could be a hardware register, memory location orother low-level location. In one embodiment a location holding afunction pointer value could be a virtual register, a source languageobject, Static-Single Assignment (SSA) name, or other compiler generatedlocation.

Aspects of the use of the local entry point with an indirect functioncall shown and described in FIGS. 1 and 3-12, employ one or more toolsto support use of the local entry point with an indirect function call.Referring to FIG. 13, a block diagram (1300) is provided illustrating acomputer system that supports and enables the use of the local entrypoint with an indirect function call. A client machine, client₀ (1330)is shown configured with a processing unit (1302) in communication witha memory (1304) across a bus (1322), and in communication with a networkof shared resources (1332) across a network connection to provide theclient₀ (1330) with access to shared resources, including, but notlimited to, shared data resources (1334), other client machines, client₁(1340) and client₂ (1342), and servers, server₀ (1350) and server₁(1352). Application object code (1306), which is generated from programsource code (not shown) by a compiler, such as compiler (1310),comprises a plurality of functions, and is stored in memory (1304) forexecution by processor (1302). The application object code (1306) may begenerated by a compiler that is located on a different machine fromclient machine, client₀, (1330). A relocation record (1320), which isgenerated by a compiler, such as a compiler (1310), is stored in theapplication object code (1306) for review by the compiler (1310), linker(1312) or loader (1314). The linker (1312) may read the relocationrecord (1320) and if necessary generate another copy of the relocationinto an executable or DSO file. The linker (1312) links the applicationobject code (1306) before the application object code (1306) is executedby the loader (1314). Shared library (1308) comprises functions that areexternal to application object code (1306) and that may be called duringexecution of application object code (1306) via external function calls(i.e., calls to functions in other modules). Loader (1314) comprisesruntime components and executes the application object code (706). Theloader (1314) may inspect the relocation record present in theexecutable or DSO file while loading the file into a memory, such asmain memory (1304).

TOC register (1316) is located in processor (1302). TOC register storesa current value of a TOC pointer for the currently active function ofapplication object code (1306) or shared library (1308). Functionaddress register (1318) is also located in processor (1302), and holdsan address of currently executing functions. In some embodiments, thecomputer system (1300) may further comprise another object code modulethat is distinct from the application object code (1306) and the sharedlibrary (1308), and the other object code module may also containfunctions that are called by application object code (1306) via externalfunction calls.

The shared data resource, such as resource (1334) may be in the form ofa storage array. The array is commonly configured with a storagecontroller to manage two or more storage devices The storage array canbe one dimensional with a single category of storage devices, or in oneembodiment multi-dimensional, also referred to herein as a tieredstorage solution with multiple types of storage, e.g. persistent RAM,SSD, HDD, and Tape. More specifically, tiered storage directs data to astorage media within the storage array based on performance,availability, and recovery requirements.

Aspects of the functional tools, e.g. compiler (110), loader (112) andlinker (114), and their associated functionality may be embodied in acomputer system/server in a single location, or in one embodiment, maybe configured in a cloud based system sharing computing resources. Withreferences to FIG. 14, a block diagram (1400) is provided illustratingan example of a computer system/server (1402), hereinafter referred toas a host (1402) in communication with a cloud based support system, toimplement the processes described above with respect to FIGS. 1 and3-12. Host (1402) is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with host (1402) include,but are not limited to, personal computer systems, server computersystems, thin clients, thick clients, hand-held or laptop devices,multiprocessor systems, microprocessor-based systems, set top boxes,programmable consumer electronics, network PCs, minicomputer systems,mainframe computer systems, and file systems (e.g., distributed storageenvironments and distributed cloud computing environments) that includeany of the above systems, devices, and their equivalents.

Host (1402) may be described in the general context of computersystem-executable instructions, such as program modules, being executedby a computer system. Generally, program modules may include routines,programs, objects, components, logic, data structures, and so on thatperform particular tasks or implement particular abstract data types.Host (1402) may be practiced in distributed cloud computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed cloud computingenvironment, program modules may be located in both local and remotecomputer system storage media including memory storage devices.

As shown in FIG. 14, host (1402) is shown in the form of ageneral-purpose computing device. The components of host (1402) mayinclude, but are not limited to, one or more processors or processingunits (1404), a system memory (1406), and a bus (1408) that couplesvarious system components including system memory (1406) to processor(1404). Bus (1408) represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus. Host (1402) typicallyincludes a variety of computer system readable media. Such media may beany available media that is accessible by host (1402) and it includesboth volatile and non-volatile media, removable and non-removable media.

Memory (1406) can include computer system readable media in the form ofvolatile memory, such as random access memory (RAM) (1412) and/or cachememory (1414). By way of example only, storage system (1416) can beprovided for reading from and writing to a non-removable, non-volatilemagnetic media (not shown and typically called a “hard drive”). Althoughnot shown, a magnetic disk drive for reading from and writing to aremovable, non-volatile magnetic disk (e.g., a “floppy disk”), and anoptical disk drive for reading from or writing to a removable,non-volatile optical disk such as a CD-ROM, DVD-ROM or other opticalmedia can be provided. In such instances, each can be connected to bus(1408) by one or more data media interfaces.

Program/utility (1418), having a set (at least one) of program modules(1420), may be stored in memory (1406) by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystems, one or more application programs, other program modules, andprogram data or some combination thereof, may include an implementationof a networking environment. Program modules (1420) generally carry outthe functions and/or methodologies of embodiments to assign global andlocal entry points for a function call and optimize an indirect callsite. For example, the set of program modules (1420) may include themodules configured to allow the use of the local entry point with anindirect function call and optimization of an indirect call site asdescribed in FIGS. 1 and 3-12.

Host (1402) may also communicate with one or more external devices(1440), such as a keyboard, a pointing device, etc.; a display (1450);one or more devices that enable a user to interact with host (1402);and/or any devices (e.g., network card, modem, etc.) that enable host(1402) to communicate with one or more other computing devices. Suchcommunication can occur via Input/Output (I/O) interface(s) (1410).Still yet, host (1402) can communicate with one or more networks such asa local area network (LAN), a general wide area network (WAN), and/or apublic network (e.g., the Internet) via network adapter (1430). Asdepicted, network adapter (1430) communicates with the other componentsof host (1402) via bus (1408). In one embodiment, a plurality of nodesof a distributed file system (not shown) is in communication with thehost (1402) via the I/O interface (1410) or via the network adapter(1430). It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with host(1402). Examples, include, but are not limited to: microcode, devicedrivers, redundant processing units, external disk drive arrays, RAIDsystems, tape drives, and data archival storage systems, etc.

In this document, the terms “computer program medium,” “computer usablemedium,” and “computer readable medium” are used to generally refer tomedia such as main memory (1406), including RAM (1412), cache (1414),and storage system (1416), such as a removable storage drive and a harddisk installed in a hard disk drive.

Computer programs (also called computer control logic) are stored inmemory (1406). Computer programs may also be received via acommunication interface, such as network adapter (1430). Such computerprograms, when run, enable the computer system to perform the featuresof the present embodiments as discussed herein. In particular, thecomputer programs, when run, enable the processing unit (1404) toperform the features of the computer system. Accordingly, such computerprograms represent controllers of the computer system.

The present embodiments may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent embodiments.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present embodiments may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present embodiments.

In one embodiment, host (1402) is a node (1460) of a cloud computingenvironment. As is known in the art, cloud computing is a model ofservice delivery for enabling convenient, on-demand network access to ashared pool of configurable computing resources (e.g., networks, networkbandwidth, servers, processing, memory, storage, applications, virtualmachines, and services) that can be rapidly provisioned and releasedwith minimal management effort or interaction with a provider of theservice. This cloud model may include at least five characteristics, atleast three service models, and at least four deployment models. Exampleof such characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting for loadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 15, an illustrative cloud computing network(1500). As shown, cloud computing network (1500) includes a cloudcomputing environment (1505) having one or more cloud computing nodes(1510) with which local computing devices used by cloud consumers maycommunicate. Examples of these local computing devices include, but arenot limited to, personal digital assistant (PDA) or cellular telephone(1554A), desktop computer (1554B), laptop computer (1554C), and/orautomobile computer system (1554N). Individual nodes within nodes (1510)may further communicate with one another. They may be grouped (notshown) physically or virtually, in one or more networks, such asPrivate, Community, Public, or Hybrid clouds as described hereinabove,or a combination thereof. This allows cloud computing environment (1500)to offer infrastructure, platforms and/or software as services for whicha cloud consumer does not need to maintain resources on a localcomputing device. It is understood that the types of computing devices(1554A)-(1554N) shown in FIG. 15 are intended to be illustrative onlyand that the cloud computing environment (1505) can communicate with anytype of computerized device over any type of network and/or networkaddressable connection (e.g., using a web browser).

Referring now to FIG. 16, a set of functional abstraction layersprovided by the cloud computing network of FIG. 15 is shown. It shouldbe understood in advance that the components, layers, and functionsshown in FIG. 16 are intended to be illustrative only, and theembodiments are not limited thereto. As depicted, the following layersand corresponding functions are provided: hardware and software layer(1610), virtualization layer (1620), management layer (1630), andworkload layer (1640). The hardware and software layer (1610) includeshardware and software components. Examples of hardware componentsinclude mainframes, in one example IBM® zSeries® systems; RISC (ReducedInstruction Set Computer) architecture based servers, in one example IBMpSeries® systems; IBM xSeries® systems; IBM BladeCenter® systems;storage devices; networks and networking components. Examples ofsoftware components include network application server software, in oneexample IBM WebSphere® application server software; and databasesoftware, in one example IBM DB2® database software. (IBM, zSeries,pSeries, xSeries, BladeCenter, WebSphere, and DB2 are trademarks ofInternational Business Machines Corporation registered in manyjurisdictions worldwide).

Virtualization layer (1620) provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer (1630) may provide the followingfunctions: resource provisioning, metering and pricing, user portal,service level management, and SLA planning and fulfillment. Resourceprovisioning provides dynamic procurement of computing resources andother resources that are utilized to perform tasks within the cloudcomputing environment. Metering and pricing provides cost tracking asresources are utilized within the cloud computing environment, andbilling or invoicing for consumption of these resources. In one example,these resources may comprise application software licenses. Securityprovides identity verification for cloud consumers and tasks, as well asprotection for data and other resources. User portal provides access tothe cloud computing environment for consumers and system administrators.Service level management provides cloud computing resource allocationand management such that required service levels are met. Service LevelAgreement (SLA) planning and fulfillment provides pre-arrangement for,and procurement of, cloud computing resources for which a futurerequirement is anticipated in accordance with an SLA.

Workloads layer (1640) provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include, but are notlimited to: mapping and navigation; software development and lifecyclemanagement; virtual classroom education delivery; data analyticsprocessing; transaction processing; and using a local entry point withan indirect function call.

As will be appreciated by one skilled in the art, the aspects may beembodied as a system, method, or computer program product. Accordingly,the aspects may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.), or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “circuit,”“module,” or “system.” Furthermore, the aspects described herein maytake the form of a computer program product embodied in one or morecomputer readable medium(s) having computer readable program codeembodied thereon.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

The embodiments are described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems), andcomputer program products. It will be understood that each block of theflow chart illustrations and/or block diagrams, and combinations ofblocks in the flow chart illustrations and/or block diagrams, can beimplemented by computer program instructions. These computer programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the flow chart and/or block diagram block orblocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flow chart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions, which execute on thecomputer or other programmable apparatus, provide processes forimplementing the functions/acts specified in the flow chart and/or blockdiagram block or blocks.

The flow charts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments. In this regard, each block in the flow charts or blockdiagrams may represent a module, segment, or portion of code, whichcomprises one or more executable instructions for implementing thespecified logical function(s). It should also be noted that, in somealternative implementations, the functions noted in the block may occurout of the order noted in the figures. For example, two blocks shown insuccession may, in fact, be executed substantially concurrently, or theblocks may sometimes be executed in the reverse order, depending uponthe functionality involved. It will also be noted that each block of theblock diagrams and/or flow chart illustration(s), and combinations ofblocks in the block diagrams and/or flow chart illustration(s), can beimplemented by special purpose hardware-based systems that perform thespecified functions or acts, or combinations of special purpose hardwareand computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used herein, thesingular forms “a”, “an” and “the” are intended to include the pluralforms as well, unless the context clearly indicates otherwise. It willbe further understood that the terms “comprises” and/or “comprising,”when used in this specification, specify the presence of statedfeatures, integers, steps, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,integers, steps, operations, elements, components, and/or groupsthereof.

The embodiments described herein may be implemented in a system, amethod, and/or a computer program product. The computer program productmay include a computer readable storage medium (or media) havingcomputer readable program instructions thereon for causing a processorto carry out the embodiments described herein.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmissions, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

The embodiments are described herein with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems), andcomputer program products. It will be understood that each block of theflow chart illustrations and/or block diagrams, and combinations ofblocks in the flow chart illustrations and/or block diagrams, can beimplemented by computer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flow chart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flow chart and/or block diagram blockor blocks.

It will be appreciated that, although specific embodiments have beendescribed herein for purposes of illustration, various modifications maybe made without departing from the spirit and scope of the specificembodiments described herein. Accordingly, the scope of protection islimited only by the following claims and their equivalents.

Aspects of the present embodiments are described herein with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerreadable program instructions.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present embodiments has been presented for purposesof illustration and description, but is not intended to be exhaustive orlimited to the embodiments in the form disclosed.

Indeed, executable code could be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different applications, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within the tool, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single dataset, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, as electronic signals on a system or network.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of agents, to provide a thorough understanding of the disclosedembodiments. One skilled in the relevant art will recognize, however,that the embodiments can be practiced without one or more of thespecific details, or with other methods, components, materials, etc. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of theembodiments.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present embodiments have been presented for purposesof illustration and description, but is not intended to be exhaustive orlimited to the embodiments in the form disclosed.

Many modifications and variations will be apparent to those of ordinaryskill in the art without departing from the scope and spirit of theembodiments. The embodiment was chosen and described in order to bestexplain the principles of the embodiments and the practical application,and to enable others of ordinary skill in the art to understand theembodiments for various embodiments with various modifications as aresuited to the particular use contemplated. Accordingly, theimplementation of determining which entry points can be used in computersystems provides a way to use local entry points with an indirect callfunction.

It will be appreciated that, although specific embodiments have beendescribed herein for purposes of illustration, various modifications maybe made without departing from the spirit and scope of the embodiments.In particular, the compiler, linker and loader can be located on adifferent computer system than the application object code. In a furtherembodiment, the loader is dynamic. In a further embodiment, the linkeris static. In another embodiment, the linker is dynamic. Accordingly,the scope of protection of these embodiments is limited only by thefollowing claims and their equivalents.

What is claimed is:
 1. A method for generate program code for anapplication module at least partially defining an indirect function callconfiguration, comprising: loading a first address of a function byusing a first symbolic reference; determining that an employed value ofthe first symbolic reference is used solely to perform the indirectfunction call in the application module; and indicating, in thegenerated program code, that the first symbolic reference can beresolved using a local entry point address of the function; and using arelocation record associated with the first symbolic reference in thegenerated program code, wherein the generated program code contains arelocation record, and the relocation record includes informationselected from the group consisting of: a location, a name of a targetsymbol, and a relocation type of an action to perform.
 2. The method ofclaim 1, wherein indicating that the first symbolic reference can beresolved using the local entry point address of the function furthercomprises inserting the local entry point address in the generatedprogram code.
 3. The method of claim 1, wherein indicating that thefirst symbolic reference cannot be resolved using the local entry pointaddress of the function further comprises inserting a global entry pointaddress in the generated program code.
 4. The method of claim 1, furthercomprising indicating the first symbolic reference can be resolved by alinker or a loader.
 5. The method of claim 1, further comprisingassessing a location holding a function pointer value, includingdetermining a full set of all references to the location is known.
 6. Acomputer system comprising: a memory; a processor, communicativelycoupled to the memory; a compiler in communication with the processor,the compiler to generate program code for an application module at leastpartially defining an indirect function call configuration, includingthe compiler to: load a first address of a function by using a firstsymbolic reference; determine that an employed value of the firstsymbolic reference is used solely to perform the indirect function callin the application module; and indicate, in the generated program code,that the first symbolic reference can be resolved using a local entrypoint address of the function; and use a relocation record associatedwith the first symbolic reference, wherein the generated program codecontains a relocation record, and the relocation record includesinformation selected from the group consisting of: a location, a name ofa target symbol, and a relocation type of an action to perform.
 7. Thesystem of claim 6, wherein the indication that the first symbolicreference can be resolved using the local entry point address of thefunction further comprises the compiler to insert the local entry pointaddress in the generated program code.
 8. The system of claim 6, whereinthe indication that the first symbolic reference cannot be resolvedusing the local entry point address of the function further comprisesthe compiler to insert a global entry point address in the generatedprogram code.
 9. The system of claim 6, further comprising a linker or aloader to resolve the first symbolic reference.
 10. The system of claim6, further comprising the compiler to indicate the first symbolicreference can be resolved by a linker or a loader.
 11. The system ofclaim 6, further comprising the compiler to assess a location holding afunction pointer value, including determine a full set of all referencesto the location is known.
 12. A computer program product for resolving afunction address, the computer program product comprising a computerreadable storage device having program code embodied therewith, theprogram code executable by a processor to: load a first address of afunction by using a first symbolic reference; determine that an employedvalue of the first symbolic reference is used solely to perform theindirect function call in the application module; and indicate, in thegenerated program code, that the first symbolic reference can beresolved using a local entry point address of the function; and use arelocation record associated with the first symbolic reference in thegenerated program code, wherein the generated program code contains arelocation record, and the relocation record includes informationselected from the group consisting of: a location, a name of a targetsymbol, and a relocation type of an action to perform.
 13. The computerprogram product of claim 12, wherein the indication that the firstsymbolic reference can be resolved using the local entry point addressof the function further comprises the program code to insert the localentry point address in the generated program code.
 14. The computerprogram product of claim 12, wherein the indication that the firstsymbolic reference cannot be resolved using the local entry pointaddress of the function further comprises program code to insert aglobal entry point address in the generated program code.
 15. Thecomputer program product of claim 12, further comprising program code toindicate the first symbolic reference can be resolved by a linker or aloader.
 16. The computer program product of claim 12, further comprisingprogram to assess a location holding a function pointer value, includingdetermine a full set of all references to the location is known.